fix(nextjs): Don't report NEXT_REDIRECT from browser
#14440
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I've read the Contributing Guide and know that testing is required, but I don't know how to test this one.... sorry... |
lforst
approved these changes
Nov 25, 2024
|
Thanks! |
mydea
pushed a commit
that referenced
this pull request
Nov 25, 2024
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #14440 Co-authored-by: chargome <20254395+chargome@users.noreply.github.com>
Closed
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #14436
Reduces error spam by not reporting
NEXT_NOT_FOUNDerror which get thrown when use theredirect()functions.From ServerComponents were addressed in #7642 and ServerAction in #10474, but this PR addresses what is reported from the Client (Browser).